Electric vehicle charging station

ABSTRACT

This disclosure is directed to methods and systems for charging an electric vehicle. A charging system may be used to charge the energy storage devices of an electric vehicle by using the power generation or regeneration systems or devices of the vehicle. The vehicle may access the charging system by positioning one or more wheels of the vehicle adjacent to, or on top of, one or more drive rollers of the charging system. The driver rollers may be rotatably coupled to one or more motors. A controller may control operation of the charging system, including the charging of the vehicle, by causing the motor to cause the drive rollers to rotate. The wheels of the vehicle may rotate in response to rotation of the drive rollers, causing power generation or regeneration systems of the vehicle to generate energy to store in an energy storage device of the vehicle.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/690,916, filed Mar. 9, 2022. The disclosure of each of theaforementioned applications is incorporated herein in its entirety forall purposes.

FIELD OF THE DISCLOSURE

The present disclosure relates to an electric vehicle charging stationor system.

BACKGROUND

Electric vehicles derive locomotion power from electricity oftenreceived from an energy storage device within the electric vehicle.Electric vehicles are often proposed to have an energystorage/containment device, such as a battery, that is charged throughsome type of wired or wireless connection at one or more stationarylocations, for example household or commercial supply sources. The wiredcharging connections require cables or other similar connectors tophysically and electrically connect the energy storage device of thevehicle to a stationary power supply. The wireless charging connectionsrequire antenna(s) or other similar structures to wirelessly connect tothe energy storage device of the vehicle a power supply that generates awireless field via its own antenna(s). However, such wired and wirelessstationary charging systems may be inconvenient, cumbersome, may posesafety risks and may have other drawbacks, such as degradation duringenergy transference, inefficiencies or losses, and so forth.

SUMMARY

Various embodiments of systems, methods and devices within the scope ofthe appended claims each have several aspects, no single one of which issolely responsible for the desirable attributes described herein.Without limiting the scope of the appended claims, the description belowdescribes some prominent features.

Details of one or more embodiments of the subject matter described inthis specification are set forth in the accompanying drawings and thedescription below. Other features, aspects, and advantages will becomeapparent from the description, the drawings, and the claims. Note thatrelative dimensions of the following figures may not be drawn to scale.

The present disclosure provides a system for charging a stationaryelectric vehicle using power generation or regeneration devices of thevehicle. The system may comprise: one or more drive rollers rotatablycoupled to one or more wheels of the vehicle and configured to rotateand thereby cause the wheels of the vehicle to rotate; one or moremotors rotatably coupled to the drive rollers and configured to causethe drive rollers to rotate; a plurality of spindle rollers rotatablycoupled to the wheels of the vehicle; a controller, comprising aprocessor. The controller may be configured to: communicate with themotors to transmit data to the motors and receive data from the motors;generate instructions for a charging sequence of the charging system.The instructions may comprise a determined angular velocity at which torotate the drive rollers; and transmit the instructions to the motors ofthe charging system to cause the motors to rotate the drive rollers atthe determined angular velocity; and a power source electrically coupledto the motors and controller and configured to provide power to themotors and controller.

In some embodiments, the power source may not be directly electricallycoupled to the vehicle.

In some embodiments, the drive rollers may be configured to be locatedat a substantially ground surface height.

In some embodiments, the system may further comprise a ramp configuredto rest on a ground surface, and the drive rollers may be configured ata top portion of the ramp.

In some embodiments, the controller may comprise a handheld devicecomprising an interactive user interface.

In some embodiments, the controller may be configured to: receive a userinput; and generate the instructions for the charging sequence based, atleast in part, on the user input.

In some embodiments, the controller may be configured to: receiveoperational settings relating to a charging sequence, and theoperational settings may be received from a memory of the controller, anexternal data store, or the vehicle; and generate the instructions forthe charging sequence based, at least in part, on the operationalsettings.

In some embodiments, the controller may be configured to communicatewith the motors wirelessly.

In some embodiments, the controller may be included in the vehicle.

In some embodiments, the controller may be configured to communicatewith the vehicle to transmit data to the vehicle and receive data fromthe vehicle.

In some embodiments, the controller may be configured to: receive datafrom the vehicle relating to charging requirements of the vehicle; andgenerate the instructions for the charging sequence based, at least inpart, on the data from the vehicle relating to the chargingrequirements.

In some embodiments, the controller may be configured to receive datafrom the vehicle relating to an identity of the vehicle or permissionsof the vehicle to access the charging system to be charged.

In some embodiments, the controller may be configured to: determine,based on the identity of the vehicle or the permissions of the vehicle,whether the vehicle has permission to access the charging system to becharged; and in response to determining that the vehicle has permissionto access the charging system, generate the instructions for thecharging sequence of the charging system.

In some embodiments, the system may further comprise a stop plateconfigured to: communicate with the controller to transmit data to thecontroller and receive data from the controller; and transition betweenan upward position and a downward position in response to instructionsreceived from the controller. In the upward position, the stop plate maybe configured to prevent the vehicle from accessing the charging systemto be charged, and in the downward position the stop plate may beconfigured to allow the vehicle to access the charging system to becharged.

In some embodiments, the controller may be configured to verifypermissions of the vehicle prior to transmitting instructions to thestop plate to transition to the downward position.

The present disclosure provides a method for charging a stationaryelectric vehicle using power generation or regeneration devices of thevehicle. The method may comprise: under control of a processor of acontroller of a charging system: generating instructions for a chargingsequence, and the instructions may comprise a determined angularvelocity at which to rotate one or more drive rollers of the chargingsystem; and transmitting the instructions, from the controller, to amotor of the charging system; in response to receiving the instructionsat the motor, causing the motor to rotate the drive rollers at thedetermined angular velocity; and by the rotation of the drive rollers atthe determined angular velocity, causing one or more wheels of thevehicle to rotate, and rotation of said wheels of the vehicle may causepower generation or regeneration devices of the vehicle to generate anelectric charge to store in an energy storage device of the vehicle.

In some implementations, the method may further comprise: receiving, atthe controller, data from the vehicle relating to charging requirementsof the vehicle; receiving, at the controller, user input; and generatingthe instructions for the charging sequence based at least in part on theuser input or the data from the vehicle.

In some implementations, the method may further comprise: verifying, bythe controller, permissions of the vehicle to access the charging systemto be charged; determining, according to the permissions whether thevehicle has permission to access the charging system to be charged; inresponse to determining that the vehicle has permission to access thecharging system to be charged: generating, at the controller,instructions to place a stop plate of the charging system in a downwardposition; transmitting, from the controller, said instructions to thestop plate to place the stop plate in the downward position to allow thevehicle to access the charging system; and generating, at thecontroller, the instructions for the charging sequence; and in responseto determining that the vehicle does not have permission to access thecharging system to be charged: generating, at the controller,instructions to place the stop plate of the charging system in an upwardposition; transmitting, from the controller, said instructions to thestop plate to place the stop plate in the upward position to prevent thevehicle from accessing the charging system; and not generating, at thecontroller, the instructions for the charging sequence.

The present disclosure provides a method for charging a stationaryelectric vehicle using power generation or regeneration devices of thevehicle. The method may comprise: under control of a processor of acontroller of a charging system: establishing communication between thecontroller and the vehicle; receiving data from the vehicle comprisingcharging requirements of the vehicle or operational settings relating tocharging the vehicle; receiving user input relating to charging thevehicle; determining, based at least in part on the user input or thedata from the vehicle, an angular velocity at which to rotate one ormore drive rollers of the charging system; generating instructions forcausing a motor to rotate the drive rollers at the determined angularvelocity; transmitting the instructions to the motor to cause the motorto rotate the drive rollers at the determined angular velocity, androtation of the one or more drive rollers may cause one or more wheelsof the vehicle to rotate, and rotation of the one or more wheels of thevehicle may cause the vehicle to generate and store an electric charge;receiving, at the controller and from the vehicle, data relating to acharge status of the vehicle; determining, based at least in part on thedata relating to the charge status whether the vehicle is fully charged;in response to determining that the vehicle is fully charged, generatinginstructions to cause the motor to stop rotating the drive rollers;transmitting the instructions to the motor to cause the motor to stoprotating the drive rollers.

In some implementations, the method may further comprise: determining,an identity of the vehicle and permissions associated with the vehicle;determining, according to the identity and permissions whether thevehicle has permission to access the charging system to be charged; inresponse to determining that the vehicle has permission to access thecharging system to be charged: generating the instructions for causingthe motor to rotate the drive rollers at the determined angularvelocity; and transmitting the instructions to the motor to cause themotor to rotate the drive rollers at the determined angular velocity;and in response to determining that the vehicle does not have permissionto access the charging system to be charged: not generating theinstructions for causing the motor to rotate the drive rollers at thedetermined angular velocity; and not transmitting the instructions tothe motor to cause the motor to rotate the drive rollers at thedetermined angular velocity.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1B are schematic diagrams illustrating side-views of exampleembodiments of an electric vehicle charging system.

FIG. 1C is a schematic diagram illustrating a top view of an exampleembodiment of an electric vehicle charging system.

FIGS. 1D-1F illustrate example embodiments of an electric vehiclecharging system.

FIG. 1G is a schematic diagram illustrating a side view of an exampleembodiment of an electric vehicle charging system.

FIG. 2A is a flowchart illustrating an example process for validating avehicle's identity prior to initiating a charging sequence.

FIG. 2B is a flowchart illustrating an example process for charging avehicle.

FIG. 3A is a flowchart illustrating an example process for validating avehicle's identity to control operation of a stop plate of a chargingsystem.

FIG. 3B is a flowchart illustrating an example process for controllingthe operation of a stop plate of a charging system.

DETAILED DESCRIPTION Overview

Example embodiments and implementations of an electric vehicle chargingstation or system are described herein. The charging system may be usedto charge any type of vehicle, such as commercial vehicles, trucks,semi-trucks, buses, vans, cars, trains, motorcycles, scooters, bicyclesand the like. The charging system can utilize the power generation orregeneration systems of the vehicle to produce a charge or voltage to bestored in an energy storage device of the vehicle. For example, thecharging system can cause one or more wheels of a vehicle to rotate.Rotation of the wheels may cause the energy storage systems of thevehicle to generate a charge which may be stored in the vehicle's energystorage devices. The charging system may be capable of completelycharging a vehicle (e.g., an energy storage device of a vehicle) in arelatively short time frame, such as about less than twenty minutes,less than ten minutes, or less than five minutes.

Advantageously, in some embodiments, the electric vehicle chargingstation or system described herein may not require a direct electricalconnection to be established between the vehicle or the vehiclescomponents and a power source (e.g., via a plug) in order to charge thevehicle (e.g., an energy storage device of the vehicle).

Example Systems and Embodiments for an Electric Vehicle Charger

FIG. 1A is a schematic diagram illustrating a side-view of an exampleembodiment of an electric vehicle charging station or system 100 (e.g.,charging system 100). The electric vehicle charging system 100 may beconfigured to charge an electric vehicle or its various components suchas an energy storage device (e.g., a battery, capacitor etc.). Theelectric vehicle charging system 100 can charge the electric vehicle byutilizing the vehicle's energy generation or regeneration capabilities.For example, the electric vehicle charging system 100 can rotate one ormore wheels of the vehicle to cause the vehicle power generation orregeneration systems to create a charge to store in (e.g., charge thevoltage of) the energy storage devices (e.g., battery, capacitor) of thevehicle. The vehicle may be stationary while the vehicle wheel(s) arerotating and the vehicle charging is occurring. The vehicle may be in adrive gear while the vehicle wheel(s) are rotating and the vehiclecharging is occurring. The vehicle may not be providing power to thevehicle motor or may be providing power to the motor while the vehiclewheel(s) are rotating and the vehicle charging is occurring.

The electric vehicle charging system 100 may include one or more ramps101 a, 101 b, one or more spindle rollers 103 a, 103 b, one or moredrive rollers 105, a stop plate 117, a controller 111, one or moremotors 113 and a power source 115. The roller(s) 105 may be rotatablycoupled to a vehicle wheel 107 and may cause the vehicle wheel 107 torotate to generate energy to charge an energy storage device of thevehicle. FIG. 1A is provided as an example embodiment of the electricvehicle charging system described herein and is not meant to belimiting. In some embodiments the charging system may include more orless components than what is shown in FIG. 1A and/or may includecomponents in a different configuration than what is shown in FIG. 1A.

The electric vehicle charging system 100 may include one or more ramps101 a, 101 b. Ramp 101 a may be an on-ramp. Ramp 101 b may be anoff-ramp. On-ramp 101 a may be configured to facilitate a vehicledriving onto the electric vehicle charging system 100 such that thevehicle wheel(s) 107 are in contact with the roller(s) 103, 105. Forexample, a vehicle may drive up the on-ramp 101 a into position to becharged such that one or more wheels 107 of the vehicle are rotatablycoupled with the rollers 103, 105. Off-ramp 101 b may be configured tofacilitate a vehicle driving off of the electric vehicle charging system100 after no more charging is desired, for example, after the vehiclehas been fully charged.

The wheel 107 may be any wheel or other similar rotation device of thevehicle. In some embodiments, the wheel 107 may be a wheel used to drivethe vehicle. In some embodiments, the wheel 107 may be a wheel that isnot used to drive the vehicle but is devoted solely to power generationor regeneration. In some embodiments, the wheel 107 may have been addedto the vehicle after initial manufacturing of the vehicle such as anadd-on component. In some embodiments, the charging system 100 may beconfigured to receive and rotate multiple wheels of a vehicle at thesame time.

The charging system 100 may be configured to receive and rotate any sizeof wheel of any vehicle type. For example, the charging system 100 mayreceive and rotate the wheels of a semi-truck or the wheels of a farm orlawn equipment such as a tractor or lawn mower or may receive and rotatethe wheels of a bicycle or scooter or motorcycle or any other vehicle asrequired or desired.

The electric vehicle charging system 100 may include one or more spindlerollers 103 a, 103 b and one or more drive rollers 105. In someembodiments, the charging system 100 may include any number of spindlerollers 103 a, 103 b as required or desired such as three, four, five,six or more than six spindle rollers 103, 103 b. In some embodiments,the charging system 100 may include two spindle rollers 103 a, 103 b, asshown in FIG. 1A. In some embodiments, the charging system 100 mayinclude any number of drive rollers 105 as required or desired such astwo, three, four, five, six or more than six drive rollers 105. In someembodiments, the charging system 100 may include one drive roller 105,as shown in FIG. 1A. The roller(s) 103, 105 may be sized as required ordesired to optimize vehicle wheel 107 rotation and vehicle charging. Insome embodiments, the rollers 103, 105 may be of a smaller diameter thanthe wheel 107. In some embodiments, the rollers 103, 105 may be of alarger diameter than the wheel 107. The roller(s) 103, 105 may be sizedindependently of one another.

The roller(s) 103, 105 may be configured to rotate at one or moreangular velocities as required or desired. For example, the angularvelocity of the drive roller 105 may be set or adjusted automatically ormanually. Increasing the angular velocity of the drive roller 105 mayincrease an angular velocity of the wheel 107 which may in turn shortenthe time required to charge the vehicle.

The roller(s) 103, 105 may be configured in an arrangement to hold avehicle wheel 107 such that a vehicle may rest in a stationary positionwhile being charged by the charging system 100. For example, theroller(s) 103, 105 may be configured to prevent the vehicle from rollingaway from the charging system 100 via the ramps 101 a, 101 b while thewheel 107 is rotating and the vehicle is being charged. In someembodiments, the roller(s) 103, 105 may be positioned such that a rollerpositioned at a centermost location between the ramps 101 a, 101 b(which may be drive roller 105) may be lower than the adjacent rollerson either side (which may be rollers 103 a, 103 b), as shown in FIG. 1A,to facilitate holding the vehicle in a stationary location while thewheel 107 is rotating and charging is occurring.

The drive roller(s) 105 may be electrically and/or mechanically coupledto a motor 113. For example, drive roller 105 may be rotatably coupledto the motor 113 via a rotational coupling 109. The rotational coupling109 may comprise one or more of a shaft, gear, pulley, belt, chain orother similar components or devices configured to transfer a mechanicalforce such as a rotational force from the motor to the drive roller 105.The motor 113 may generate a rotational force which may be applied tothe drive roller 105 via the rotational coupling 109. The motor 113 maycause the drive roller 105 to rotate. Rotation of the drive roller 105may cause the wheel 107 to rotate. Rotation of the wheel 107 may causethe energy generation or regeneration systems of the vehicle to create acharge to charge a voltage of the energy storage device(s) of thevehicle.

In some embodiments, the spindle roller(s) 103 a, 103 b may beconfigured to rotate freely. For example, the spindle roller(s) 103 a,103 b may not be directly rotatably coupled to the motor 113. Thespindle roller(s) 103 a, 103 b may rotate in response to a rotation ofthe driver roller 105 and/or a rotation of the wheel 107.

The motor 113 may be configured to cause the drive roller(s) 105 rotateat one or more angular velocities. For example, the motor 113 may beconfigured to operate at one or more operational settings such that themotor 113 causes the drive roller(s) 105 to rotate at one or moreangular velocities. Changing the angular velocity at which the driveroller(s) 105 rotate may increase or decrease the time required tocharge the vehicle. The motor 113 may be configured to cause the driveroller 105 to rotate at any angular velocity as required or desired. Theangular velocity may vary depending on the size of the drive roller 105,the size of the wheel 107, the charge required by the vehicle and/or thetime desired to charge the vehicle. In some embodiments, the motor 113may cause the drive roller 105 to rotate at or between 1000 and 2000RPMs or 2000 and 3000 RPMs or 3000 and 4000 RPMS or 4000 and 5000 RPMSor 5000 and 6000 RPMS or 6000 and 7000 RPMS or 7000 and 8000 RPMS or8000 and 9000 RPMS or 9000 and 10000 RPMS.

The motor 113 may be electrically coupled to a power source 115. Thepower source 115 may provide energy to the charging system and itsvarious components. For example, the power source 115 may power themotor 113 and/or controller 111. The power source may be any powersource capable of holding and/or conveying an electric voltage orcharge. For example, the power source 115 may comprise Mains electricityor the power grid to which the motor may be coupled via a standard 110Vor 220V outlet. The power source 115 may comprise a portable powersource such as a battery or capacitor capable of holding or storing acharge such as a voltage differential. The power source 115 may comprisea generator capable of generating or converting energy, such as acombustion generator, a solar generator, a wind generator or a hydrogenerator.

The electric vehicle charging system 100 may include a controller 111.The controller 111 may be electrically coupled to the motor 113 and/orthe power source 115. In some embodiments, the power source 115 maypower the controller 111. In some embodiments, the controller 111 maycomprise an energy storage device such as one or more batteries to powerthe operation of the controller 111.

As shown, the controller 111 may include a communication module 110, oneor more processors 106, and a storage device 108. The processor 106 canbe configured, among other things, to process data, execute instructionsto perform one or more functions, and/or control the operation of thecontroller 111, the charging system 100, and/or a vehicle. For example,the processor 106 can process data obtained from other components of thecharging system (e.g., motor 113, stop plate 117) as well as dataobtained from a vehicle (e.g., from a management system of a vehicle)and can execute instructions to perform functions related to analyzing,storing, and/or transmitting such data.

The storage device 108 can include one or more memory devices that storedata, including without limitation, dynamic and/or static random accessmemory (RAM), programmable read-only memory (PROM), erasableprogrammable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM), and the like. The storage device108 can be configured to store data such as data obtained from othercomponents of the charging system, from a vehicle, and the like. Theprocessor 106 can be configured to access the storage device 108 toretrieve the data stored therein.

The communication module 110 can facilitate communication (via wiredand/or wireless connection) between the controller 111 (and/orcomponents thereof) and separate devices, such as other components ofthe charging system 100 (e.g., motor 113, stop plate 117) or a vehicle.For example, the communication module 110 can be configured to allow thecontroller 111 to wirelessly communicate with other devices, systems,sensors, and/or networks over any of a variety of communicationprotocols. The communication module 110 can be configured to use any ofa variety of wireless communication protocols, such as Wi-Fi (802.11x),Bluetooth®, ZigBee®, Z-Wave®, cellular telephony, infrared, near-fieldcommunications (NFC), RFID, satellite transmission, proprietaryprotocols, combinations of the same, and the like. The communicationmodule 110 can allow data and/or instructions to be transmitted and/orreceived to and/or from the controller 111 and separate devices. Thecommunication module 110 can be configured to receive (for example,wirelessly) data and/or other information. The communication module 252can be configured to transmit (for example, wirelessly) data and/orother information such as instructions. For example, the communicationmodule 252 can be configured to receive and/or transmit data to othercomponents of the charging system 100 or to a vehicle, or to amanagement system of a vehicle, to a remote data store, or to the cloud,or to other devices which can include, among others, a mobile device(for example, an iOS or Android enabled smartphone, tablet, laptop), adesktop computer, a server or other computing or processing device fordisplay.

The communication module 110 can be embodied in one or more componentsthat are in communication with each other. The communication module 110can comprise a wireless transceiver, an antenna, and/or a near fieldcommunication (NFC) component, for example, an NFC transponder.

The controller 111 may be in communication (e.g., via the communicationmodule 110) with other components of the charging system 100 such as themotor 113 or the stop plate 117. The controller may be configured totransmit data to, and/or receive data from, the other components of thecharging system 100 (e.g., motor 113, stop plate 117). In someembodiments, the controller 111 may communicate (e.g., transfer orreceive data) with the other components of the charging system 100 via awired connection. In some embodiments, the controller 111 maycommunicate (e.g., transfer or receive data) with the other componentsof the charging system 100 wirelessly, for example, via a network,bluetooth technology or the like. In some embodiments, the controller111 may be configured to transmit data to, and/or receive data from(e.g., is in communication with) the vehicle that is being charged orthe components of said vehicle. For example, the controller 111 may bein communication with a battery management system (BMS) of the vehicle.The battery management system may communicate data to the controllerrelating the energy storage devices of the vehicle or power generationor regeneration systems of the vehicle, such as a charge level of theenergy storage devices, a rate of charge, a time remaining until fullycharged and the like. The controller 111 may communicate with thevehicle or components thereof, wirelessly or via a wired connection asdescribed above.

The controller 111 may be configured to communicate data to the motor113 to control the operation of the motor 113. For example, thecontroller 111 may communicate data to the motor 113 to set or adjust anangular velocity at which the motor 113 causes the drive roller 105 torotate. In some embodiments, the controller 111 may set the angularvelocity automatically. For example, the controller 111 may cause themotor 113 to operate according to preconfigured settings such as may bestored in memory on the controller 111. In some embodiments, thecontroller 111 may store settings corresponding to one or more vehicletypes which settings may cause the charging system 100 to operatedifferently as required by the various vehicle (or energy storagedevice) types. As another example, the controller 111 may cause themotor 113 to operate in response to data received at the controller fromthe motor 113 and/or the vehicle (or vehicle components such as a BMS).For example, the controller 111 may receive data from the vehicle (forexample communicated wirelessly) that the energy storage device is at acertain charge level along with other charging or voltage requirementsof the energy storage device. The controller 111 may, accordingly,communicate instructions to the motor 113 to cause the motor 113 todrive the drive roller 105 at a certain angular velocity. As anotherexample, the controller 111 may receive data from the vehicle that theenergy storage device of the vehicle is fully charged. In response, thecontroller 111 may cause the motor 113 to stop driving the drive roller105 to end the charge sequence of the vehicle.

In some embodiments, the controller 111 may operate in response to auser input. For example, the controller 111 may cause the motor 113 tooperate (e.g., drive at certain angular velocities) in response to amanual user input. A user may control operation of the charging system100 or its various devices and components via the controller 111. A usermay manually select, via the controller, the angular velocity at whichthe motor 113 drives the drive roller 105.

The controller 111 may comprise an interactive user interface such as adisplay which may display information (e.g., to a user) relating to theoperation of the charging system 100 and/or the charging sequence of thevehicle. The interactive user interface (e.g., display) may also receiveuser input to control operation of the controller and/or the chargingsystem 100. The display may be an LCD display, a capacitive touchscreenor the like. The controller 100 and/or interactive user interfacethereof may comprise input controls such as buttons, sliders, dials,knobs and the like which may be actuated via mechanical input and/or viaelectrical input such as via a capacitive touchscreen.

In some embodiments, the controller 111 may comprise a handheld device.In some embodiments, the controller 111 may comprise a phone, tablet,handheld electronic, personal computer or other similar computing deviceconfigured with an executable application to control operation of thecharging system as described herein. In some embodiments, the controller111 may be portable. In some embodiments, the controller 111 may beremote to the charging system 100 and its various other components.

In some embodiments, the controller 111 may comprise a fixed device, forexample a device that is fixed with respect to the charging system 100or the other components thereof. For example, the controller 111 maycomprise a single integrate unit with the charging system 100 or othercomponents thereof. For example, the controller 111 may be integratedinto a single unit with the motor 113 or into a single unit with one ofthe ramps 101. In some embodiments, the controller 111 may be incommunication with one or more devices remote to the charging system 100such as phone or computer.

In some embodiments, the controller 111 may be comprised as part of thevehicle that is being charged. As the vehicle enters the charging system100 to be charged the controller 111 (from within the vehicle) mayestablish a wireless connection with the other components of thecharging system 100 and may control operation of the charging system 100and its components. The controller 111 may automatically controloperation of the charging system 100 or may control operation of thecharging system 100 in response to user input at the controller 111. Asan example, the controller 111 may be comprised as part of a dashboardarea of the vehicle. A user (e.g., an operator of the vehicle) maycontrol the charging of their vehicle via the controller 111 byoperating the controller 111 on the dashboard of the vehicle.

The electric vehicle charging system 100 may include a stop plate 117.The stop plate 117 may be positioned at various locations along the ramp101, for example at a bottom portion of the ramp 101 or a top portion ofthe ramp 101. The stop plate 117 can help to keep a vehicle stationaryby preventing a vehicle from moving (e.g., rolling). For example, when avehicle wheel 107 is atop the charging system 100 such that a wheel 107is being rotated by the roller(s) 103, 105, another wheel of the vehiclemay be adjacent to the stop plate 117 such that the vehicle is blockedfrom moving. In some embodiments, one or more front wheels of thevehicle are adjacent to the stop plate 117 while one or more back wheelsare being rotated by the roller(s) 103, 105. In some embodiments, one ormore back wheels of the vehicle are adjacent to the stop plate 117 whileone or more front wheels are being rotated by the roller(s) 103, 105. Insome embodiments, one or more back or front wheels of the vehicle areadjacent to the stop plate 117 while another wheel (such as a fifthwheel) of the vehicle is being rotated by the roller(s) 103, 105.

The stop plate 117 may prevent a vehicle from driving up the ramp 101 tobe charged by the charging system 100. For example, in some embodiments,it may be desirable to select which vehicles are allowed to use thecharging system and which vehicles are not allowed to use the chargingsystem. The stop plate 117 may prevent certain vehicles from accessingthe charging system 100 to be charged.

The stop plate 117 may transition, for example as shown in FIG. 1A, froma downward position to an upward position or from an upward position toa downward position. The stop plate 117 may transition between downwardand upward positions by rotating or by translating up and down or bysome other motion. When the stop plate 117 is in the upward position,the stop plate 117 may prevent a vehicle that is being charged by thecharging system 100 from rolling and/or moving. When the stop plate 117is in the upward position, the stop plate 117 may prevent vehicles fromentering the charging system 100 to charge. Such vehicles prevented fromentering the charging system 100 may be specifically selected (e.g.,intentionally filtered) to be kept from accessing the charging system.When the stop plate 117 is in the downward position, the stop plate 117may allow a vehicle to leave the charging system 100, such as a vehiclethat has finished charging. When the stop plate 117 is in the downwardposition, the stop plate 117 may allow a vehicle to enter the chargingsystem 100. Such vehicles that are allowed to access the charging system100 may be specifically selected to be allowed to access the chargingsystem 100 to be charged.

The stop plate 117 may transition between the upward and downwardpositions automatically or manually. For example, the stop plate 117 maytransition in response to a command from the controller 111. Thecontroller 111 may communicate data (e.g., instructions) to the stopplate 117 to control operation of the stop plate 117. The controller 111may communicate data to the stop plate 117 in response to user input atthe controller 111 or automatically, for example in response to datareceived at the controller 111 and/or according to one or moreoperational settings included in the controller 111.

In some embodiments, the stop plate 117 may transition in response to asignal from a sensor which may be included in the charging system 100,such as a sensor configured to detect the location or presence of avehicle on the charging system 100 such as a motion sensor (such as anIR sensor), a weight sensor, a magnetic field detector sensor or thelike.

The stop plate 117 may include one or more actuators such as pistons,levers or the like for controlling the transition of the stop plate 117between the downward and upward positions. Electronics, for exampleincluded in the stop plate 117 or the controller 111, can control theactuators to control when the stop plate 117 transitions between thedownward and upward positions.

In some embodiments, the stop plate 117 may be manually transitionedbetween the downward and upward positions. For example, a user may liftthe stop plate 117 from a downward position to an upward position or maylower the stop plate 117 from an upward position to a downward position.

In some embodiments, the stop plate 117 may include various levels orincrements between the downward and upward positions, such as one ormore halfway positions to the which the stop plate 117 may be positionedfor various purposes. In some embodiments, the charging system 100 mayinclude more than one stop plate 117 such as a stop plate on both sidesof the charging system 100 on each of the ramps 101.

In some embodiments, the charging system 100, or portions thereof, maybe positioned above a ground surface. For example, the ramp(s) 101 mayrest on a ground surface such that the roller(s) 103, 105 are positionedat a height above the ground. In some embodiments, the charging system100 may not include one or more of the ramps 101 such that the roller(s)103, 105 are positioned at a ground surface or substantially at a groundsurface. In some embodiments, the ramps 101 may be inverted from what isshown in FIG. 1A such that the roller(s) 103, 105 are positioned below aground surface.

In some embodiments, the charging system 100 can be portable. In someembodiments, the charging system 100 can be integrated as a single unitor package. For example, the components of the charging system maycomprise a single device. For example, the motor, controller and/orpower source may be comprised as part of a ramp 101 of the chargingsystem 100.

In some embodiments, the charging system may allow more than one vehicleto access the charging system at the same time, for example to becharged at the same time.

FIG. 1B is a schematic diagram illustrating a side-view of an exampleembodiment of an electric vehicle charging system 100 (e.g., chargingsystem 100). The embodiment shown in FIG. 1B may include similarcomponents and structural and functional features as described withreference to FIG. 1A. As shown in FIG. 1B, the charging system 100 maybe integrated as a single unit. For example, one or more motor(s) 113may be housed within or adjacent to a ramp portion, stand portion orother similar portion of the charging system 100. Similarly, acontroller 111 may be housed within a ramp portion, stand portion orother similar portion of the charging system 100. In some embodiments,the motor(s) 113 may be adjacent to an axis of rotation of the rollers103, 105. For example, the motor(s) 113 may drive the rollers 103, 105via a pulley and gear system rather than via a direct connection from ashaft of the motor 113 to a shaft of the drive roller 105.

FIG. 1C is a schematic diagram illustrating an aerial view of an exampleembodiment of an electric vehicle charging system 100 (e.g., chargingsystem 100). The embodiment shown in FIG. 1C may include similarcomponents and structural and functional features as described withreference to the other Figures, such as FIG. 1A. As shown in FIG. 1C,the charging system 100 may include two motors 113 a, 113 b which may bepositioned on either side of the charging system 100. The motors 113 a,113 b may be rotatably coupled to a drive roller 105. The motors 113 a,113 b may cause the drive roller 105 to rotate, for example at a certainRPM, which can be dynamically controlled and changed by a controller.The drive roller 105 may be rotatably coupled to one or more wheels 107a, 107 b of a vehicle. Rotation of the drive roller 105 may cause thewheels 107 a, 107 b to rotate which may in turn cause the powergeneration or regeneration systems of the vehicle to store energy in anenergy storage device of the vehicle.

The charging system 100 may include one or more spindle rollers 103 a,103 b which may be configured to rotate freely (e.g., independently fromthe drive roller 105 or motors 113 a, 113 b). For example, the spindlerollers 103 a, 103 b may not be rotatably coupled to the motors 113 a,113 b or the drive roller 105. The spindle rollers 103 a, 103 b mayrotate in response to a rotation of the wheels 107 a, 107 b and may helpto support a weight of the wheels 107 a, 107 b and the vehicle.

In some embodiments, motor 113 a may drive a first drive roller andmotor 113 b may drive a second drive roller and motors 113 a, 113 b mayoperate independently from one another. In some embodiments, motor 113 aand motor 113 b may operate in unison or in a coordinate manner. In someembodiments, motors 113 a, 113 b may drive the same drive roller.

As shown in FIG. 1C, the charging system 100 can rotate more than onewheel of a vehicle at a time which may facilitate charging of thevehicle's energy storage devices. FIG. 1C shows two wheels of a vehiclebeing rotated by the charging system that are side-by-side (such as twofont wheels or two back wheels). In some embodiments, multiple wheels ofa vehicle may be rotated that are not side-by-side (such as a frontwheel and a back wheel). In some embodiments, the charging system 100can be configured to rotate any of the wheels of a vehicle as requiredor desired, such as the wheels of an 18-wheel vehicle such as asemi-truck, or the wheels of a motorcycle, or the wheels of a vehiclethat do not drive the vehicle but that are devoted solely to powergeneration or regeneration.

FIG. 1D illustrates an example embodiment of an electric vehiclecharging system 100 (e.g., charging system 100). The example embodimentshown in FIG. 1D may include similar components and structural andfunctional features as described with reference to the other Figures,such as FIG. 1A. As shown in the example embodiment of FIG. 1D, thecharging system 100 may include a ramp 101. The ramp 101 may allow avehicle to access the charging system 100 by allowing the vehicle todrive up the ramp 101 to position the wheels of the vehicle on therollers 103, 105. The ramp 101 may allow a vehicle to exit the chargingsystem 100 by allowing the vehicle to drive down the ramp 101. The sameramp 101 may be used for entering (e.g., accessing) the charging system100 and for exiting the charging system 100. In some embodiments, forexample as shown in FIG. 1A, one ramp may be used to access the chargingsystem 100 and another different ramp may be used to exit the chargingsystem 100.

As shown in FIG. 1D, the ramp 101 may include two separate portions,which may each correspond to different wheels of a vehicle. The separateportions may be placed according as desired, for example at varyingdistances from each other, to accommodate various vehicles sizesaccessing the charging system 100. For example, various vehicles mayhave wheels that are wider or narrower in distance from each other whichmay require the two portions of the ramp 101 shown in FIG. 1D to bespaced at various distances from each other. In some embodiments, theramp 101 may comprise a single unit, for example a single portion thatmay be much wider than those portions of the ramp 101 shown in FIG. 1D.A ramp with a single portion that is very wide may provide a“one-size-fits-all” implementation to allow vehicles with various wheelwidths to access the charging system 100 without needing to alter theramp 101 configuration.

In some embodiments, the ramp 101 may be configured with a steeper orshallower incline than shown in the example embodiment of FIG. 1D. Insome embodiments, the ramp 101 may be configured to change incline toaccommodate various vehicle needs.

As shown in FIG. 1D, the charging system 100 may be configured to bewide enough to allow two wheels of a vehicle to access the chargingsystem 100 to be rotated simultaneously. In some embodiments, thecharging system 100 may be wider or narrower than what is shown in theexample embodiment of FIG. 1D. For example, the charging system 100 maybe wide enough to allow two parallel wheels of a semi-truck, or otherlarge vehicle to be rotated simultaneously. In some embodiments, thecharging system 100 may be just wide enough to allow two parallel wheelsof a small car or other small vehicle to be rotated simultaneously. Insome embodiments, the charging system 100 may be just wide enough toallow only a single wheel to be rotated such as a single wheel of a caror truck or van or other multi-wheel vehicle, or a single wheel of amotorcycle or bicycle or scooter or other two-wheel vehicle.

As shown in FIG. 1D, the charging system 100 may be above a groundsurface. For example, the rollers 103, 105 and/or motor 113 may be abovea ground surface. In some embodiments, the charging system 100, orportions thereof, may be below a ground surface. For example, therollers 103, 105 may be below a ground surface or at the same height asa ground surface such that a ramp may not be needed for a vehicle toaccess the charging system 100 to have its wheel(s) rotated by theroller(s) 103, 105.

FIG. 1E illustrates an example embodiment of an electric vehiclecharging system 100 (e.g., charging system 100). The example embodimentshown in FIG. 1E may include similar components and structural andfunctional features as described with reference to the other Figures,such as FIG. 1A. As shown in the example embodiment of FIG. 1E, thecharging system 100 may include spindle rollers 103 a/b, a drive roller105 and a motor 113 such as may be described elsewhere herein.

In some embodiments, the rollers 103, 105 may be parallel to one anotherand may each be configured at varying distances from a ground surface.For example, the drive roller 105 may be positioned at a distance abovea ground surface that is less than a distance above the ground surfaceat which one or more of the spindle rollers 103 a/b are positioned. Thespindle rollers 103 a/b may be positioned at distances from a groundsurface that are the same as each other or different than each other.

As shown in the example embodiment of FIG. 1E, the rollers may bepositioned to hold the wheel(s) of a vehicle (see also FIG. 1F). Therollers may be positioned as required or desired, for example to holdwheels of various sizes. In some embodiments, the rollers 103, 105 maybe adjusted (e.g., manually and/or automatically) to accommodate andhold wheels of various sizes. Positioning the rollers 103, 105 such thatthey hold or cradle a vehicle wheel (such as shown in FIG. 1E) may allowthe rollers to rotate the vehicle wheel while simultaneously holding thevehicle wheel in the same place. In some embodiments, the rollers 103,105 may be positioned such that they contact the wheel at points aroundthe wheel circumference that would be farther apart than what is shownin FIG. 1E. This may allow for a more aggressive hold on the wheel whichmay facilitate holding the wheel in the same place which may beadvantageous when rotating the wheel, especially at larger angularvelocities and/or larger angular accelerations. Likewise, more rollers,such as spindle rollers, may be implemented to more securely hold thevehicle wheel in place while it is rotating.

In some embodiments, each of the rollers 103, 105 may be positioned at asame or similar distance from a ground surface as each of the otherrollers 103, 105. For example, the rollers 103, 105 may form a planesurface on which the wheel is positioned and rotated. In someembodiments, the rollers may be integrated as part of aconveyer-belt-like surface on which the vehicle wheel is rotated.

FIG. 1F illustrates an example embodiment of an electric vehiclecharging system 100 (e.g., charging system 100). The example embodimentshown in FIG. 1F may include similar components and structural andfunctional features as described with reference to the other Figures,such as FIG. 1A. As shown in the example embodiment of FIG. 1F, thecharging system 100 may include spindle rollers 103 a/b, a drive roller105 and a motor 113 such as may be described elsewhere herein. Thecharging system 100 may also include spindle roller pulleys 123 a/b, adrive roller pulley 125 and a belt 126. The pulleys 123, 125 maycomprise gears which may have teeth, or other similar rotatablecomponents. The belt 126 may comprise a chain. The pulleys 123, 125 maycomprise various sizes as required or desired and may all be the samesize or may be different sizes than each other.

A shaft of the motor 113 may be rotatably coupled to the drive roller105 and/or to the drive roller pulley 125. The motor 113 may directlycause the drive roller 105 and/or the drive roller pulley 125 to rotate.For example, the motor 113 may operate to cause the shaft of the motorto rotate which may in turn cause the drive roller 105 and/or the driveroller pulley 125 to rotate.

The belt 126 may be rotatably coupled to the pulleys 123, 125. In someembodiments, rotation of the drive roller pulley 125 may cause thespindle roller pulleys 123 a/b to rotate, for example, via the belt 126.In some embodiments, rotation of the drive roller pulley 125 may notcause the spindle roller pulleys 123 a/b to rotate.

The pulleys 123, 125 may be rotatably coupled to the rollers 103, 105.For example, the drive roller 105 and drive roller pulley 125 may bothrotate about a same axis of rotation and may be directly rotatablycoupled. Each of the spindle rollers 103 a/b and respective spindleroller pulleys 123 a/b may rotate about a same axis of rotation and maybe directly rotatably coupled. Rotation of the rollers 103, 105 maycause the wheel 107 to rotate which may cause an energy to be stored inan energy storage device of the vehicle. The motor 113 may cause thepulleys 123, 125 (and rollers 103, 105) to rotate at a high angularvelocity or at a low angular velocity as required or desired. Thepulleys 123, 125 (and rollers 103, 105) may rotate at a higher or lowerangular velocity than the wheel 107.

FIG. 1G is a schematic diagram illustrating an example embodiment of anelectric vehicle charging system 100 (e.g., charging system 100). Asshown, the rollers 103, 105 of the charging system 100 can be positionedat a substantially similar height as a ground surface 102 or beneath aheight of a ground surface 102. As shown, when the rollers 103, 105 areat a same height as a ground surface 102 or beneath a height of a groundsurface, a vehicle may access the charging system 100 by drivingdirectly onto the rollers 103, 105 such that the wheel 107 remains at asubstantially constant height when being rotated by the rollers 103, 105as when on a ground surface 102. In embodiments where the rollers 103,105 are at a same height as a ground surface 102 or beneath a groundsurface 102, other devices and components of the charging system 100,such as the controller 111, the motor 113, the power source 115, may bebeneath a ground surface or above a ground surface as required ordesired.

Example Methods for Charging an Electric Vehicle

FIG. 2A is a flowchart illustrating an example process 200 forvalidating a vehicle's identity prior to initiating a charging sequence.Example process 200, or any portion thereof, may be implemented on, orexecuted, by a computing device, such as a processor and in someembodiments may be implemented on a processor of a controller of thecharging system described herein such as controller 111.

At block 201, the processor can detect the presence of a vehicle on thecharging system. The processor may detect the presence of the vehicle inresponse to a signal from a sensor such as a motion sensor, a weightsensor, a magnetic field detector sensor or the like. At block 203, theprocessor may determine an identify of the detected vehicle. In someembodiments, the processor may determine the vehicle's identity byestablishing a communication (e.g., wirelessly) with the vehicle andreceiving data from the vehicle relating to the vehicle's identity. Insome embodiments, the processor may determine the vehicle's identity byreceiving user input at the controller relating the vehicle's identity.In some embodiments, the processor may determine the vehicle's identityby receiving data from one or more sensors (such as a camera) that maygather information (e.g., images) of the vehicle and transmit them tothe processor. The identity of the vehicle may include a make of thevehicle, a model of the vehicle, a year of the vehicle, a vehicleidentification number, a license plate number, an owner of the vehicle,a status of the vehicle (such as whether the vehicle has been registeredto access and use the charging system) or other such information. Byidentifying and determining a vehicle's identity, the charging systemmay be able to more easily control access to the charging system such asby allowing certain people or vehicles to use the charging system andpreventing others from using the charging system.

At block 205, the processor may determine the permissions associatedwith the vehicle. For example, the processor may maintain (e.g., inmemory), or may have access to, a list of vehicles as well aspermissions that have been granted to the vehicles. For example, theprocessor may maintain or have access to a list of vehicles registeredto access and use the charging system. Each of these vehicle's may havea permission status indicating their allowed use of the charging system.A vehicle may be registered with the charging system such that theprocessor may include the vehicle's identifying information and updatethe vehicle's permission status to grant the vehicle permission to usethe charging system. In some embodiments, a list of vehicles registeredor otherwise associated with the charging system may have tiered levelsof permissions. For example, a group of vehicles may have a firstpermission level granting them unlimited access to the charging systemand another group of vehicles may have a second permission levelgranting them limited access to the charging system, such as a limitednumber of charges or a limited number of charges per time frame. Forexample, some vehicles may only have permission to charge three timesafter which they will not be able to access the charging system to becharged, for example until they renew their registration, or somevehicles may have permission to charge their vehicle once per week.

At block 207, the processor may determine whether the vehicle haspermission to access the charging system to be charged. Thedetermination may be based on the vehicle's identity and associatedpermission as discussed above. For example, the processor may validatethe permissions associated with the vehicle and/or may verify thepermissions against some other criteria such as a history of charges,the time of the last charge, a payment history etc.

If, at block 207 the processor determines that the vehicle haspermission to access and use the charging system, the processor mayinitiate a charging sequence at block 209 to charge the vehicle.Otherwise, the processor may return to block 201 without initiating acharging sequence. In some embodiments, the processor may output amessage indicating a failure to charge and a reason for not charging incases where the processor does not initiate a charge sequence.

Process 200 is provided as an example and is not intended to belimiting. In some embodiments, the processor may not implement all theblocks shown in process 200 or may implement additional blocks to thosethat are shown in process 200. In some embodiments, the processor mayexecute the blocks in an order that is different than shown in process200. In some embodiments, the controller may initiate a chargingsequence automatically, for example upon detecting the presence of avehicle on the charging system, without validating the identify andpermissions of the vehicle. In some embodiments, the controller may onlyinitiate a charging sequence in response to a user input to initiate thecharging sequence without detecting the presence of a vehicle andwithout validating the vehicle's identity and permissions.

FIG. 2B is a flowchart illustrating an example process 250 for charginga vehicle. Example process 250, or any portion thereof, may beimplemented on, or executed, by a computing device, such as a processorand in some embodiments may be implemented on a processor of acontroller of the charging system described herein such as controller111.

At block 252, the processor may optionally establish communication withthe vehicle that is to be charged. The communication can be wireless. Atblock 254, the processor may optionally receive data from the vehicle,such as via a wireless communication. Data received from the vehicle mayrelate to the charging requirements of the vehicle such as a voltage orcharge capacity of an energy storage device of the vehicle, a desiredcharge rate of an energy storage device, a charge time, a voltagerequired to charge the energy storage device, a current required tocharge or other similar information. Data received from the vehicle mayinclude operational settings relating to a charging sequence, forexample an optimal charge sequence for charging the vehicle.

At block 256, the processor may determine the charging requirements ofthe vehicle. The processor may determine the charging requirements basedon data received from the vehicle such as at step 254 and/or based ondata stored in memory of the processor or data to which the processormay have access, such as via a network. The charging requirements mayinclude a voltage, current or amperage required to charge, a chargecapacity of the vehicle, a charge time of the vehicle, a charge rate ofthe vehicle and the like.

At block 258, the processor may optionally check for operationalsettings relating to a charging sequence for charging the vehicle. Forexample, the processor may have operational settings stored in memory ormay have access to operational settings such as on an external datastore or the vehicle. For example, the processor may receive operationalsettings from the vehicle. Operational settings may define how thecharging system operates to charge the vehicle, for example an RPM atwhich to drive the drive roller(s) or a length of time to drive thedrive roller(s). The processor may check for operational settings thatcorrespond to the charging requirements of the vehicle. For example, theprocessor may have access to various operational settings correspondingto various types of vehicles and/or types of energy storage devices ofthe vehicle (e.g., make, model, manufacturer etc.), and may check for anoperational setting that would correspond to (e.g., satisfy) thecharging requirements of the vehicle. If the processor determines anoperational setting for charging the vehicle that satisfies thevehicle's charging requirements, the processor may proceed directly toblock 262 or may proceed to block 260. If the processor determines nooperational settings are available that correspond to the vehicle'scharging requirements, the processor may proceed to block 260.

At block 260, the processor may optionally receive user input relatingto a charging sequence, for example, via the controller. For example, auser may input information relating to the charging sequence such as theRPMs at which to drive the drive roller(s), a time for which to drivethe drive roller(s), a time or command to start the charge sequence, atime or command to stop the charge sequence etc.

In some embodiments, the user input received at block 260 may overridean operational setting retrieved by the processor at block 258. In someembodiments, an operational setting retrieved by the processor at block258 may override user input received at block 260. In some embodiments,an operational setting retrieved by the processor at block 258 and auser input received at block 260 may be used simultaneously by theprocessor.

At block 262, the processor may determine an RPM at which to drive thedrive roller(s). The processor may determine the RPM based on a userinput at block 260 and/or an operational setting retrieved at block 258.At block 264, the processor may instruct the motor(s) of the chargingsystem to cause the driver roller(s) to rotate at the determined RPM.

At block 266, the processor may optionally receive data from thevehicle. This data may correspond to information relating to a chargestatus of the vehicle, such as a voltage or charge level or charge rateof an energy storage device of the vehicle. This data may indicate tothe processor a length of remaining time until the vehicle is fullycharged, an amount of remaining voltage or charge until the vehicle isfully charged or the like.

At block 268, the processor may determine whether the charge sequencehas been completed. This determination may be based on data receivedfrom the vehicle at block 266 and/or input received from a user at ablock 260. The processor may consider the charge sequence to becompleted when an energy storage device of the vehicle has been fullycharged, when a certain time has elapsed when an energy storage deviceof the vehicle has been charged by a certain amount, or when a user hasinputted a command to terminate the charge sequence etc.

If the processor determines at block 268 that the charge sequence iscomplete, the processor may terminate the charge sequence at block 270.Termination of the charge sequence can include instructing the motor(s)to cause the drive roller(s) to stop rotating.

If the processor determines at block 268 that the charge sequence iscomplete, the processor may check for user input relating to the chargesequence. For example, the processor may check to see whether a user hasinput a command to terminate the charge sequence (e.g., prior to thevehicle being fully charged). For example, a user may optionally chooseto terminate a charge sequence at any time during charging by inputtinguser input for example via the controller.

Process 250 is provided as an example and is not intended to belimiting. In some embodiments, the processor may not implement all theblocks shown in process 250 or may implement additional blocks to thosethat are shown in process 250. In some embodiments, the processor mayexecute the blocks in an order that is different than shown in process250.

FIG. 3A is a flowchart illustrating an example process 300 forvalidating a vehicle's identity to control operation of a stop plate ofa charging system. The stop plate described in process 300 may includestructural and/or operational features similar to stop plate 117described with reference to FIG. 1A. Example process 300, or any portionthereof, may be implemented on, or executed, by a computing device, suchas a processor and in some embodiments may be implemented on a processorof a controller of the charging system described herein such ascontroller 111.

At block 301, the processor may cause a stop plate to be placed in anupward position, for example by sending instructions to an actuator ofthe stop plate. When in the upward position, the stop plate may preventvehicles from accessing the charging system to be charged, for exampleby preventing vehicles from driving up a ramp.

At block 303, the processor may detect a vehicle that is approaching ornear the charging system. The processor may detect the presence of avehicle using one or more sensors as described elsewhere herein and/ormay detect a vehicle based on user input, for example at the controller,that a vehicle is near or approaching the charging system to be charged.

At block 305, the processor may determine the identity of the vehicleand at block 307 may determine the permissions associated with theidentified vehicle. At block 309, the processor may determine whetherthe vehicle has permission to access the charging system for example tobe charged. The bocks 305, 307 and 309 may include, respectively,similar implementations and embodiments as blocks 203, 205 and 207, asdescribed with reference to FIG. 2A.

At block 311, the processor may cause the stop plate to be placed in thedownward position for example by sending instructions to an actuator ofthe stop plate. When in the downward position, the stop plate may allowvehicles to access the charging system to be charged, for example byallowing vehicles to drive up a ramp to position their wheels adjacentto the drive roller(s).

Process 300 is provided as an example and is not intended to belimiting. In some embodiments, the processor may not implement all theblocks shown in process 300 or may implement additional blocks to thosethat are shown in process 300. In some embodiments, the processor mayexecute the blocks in an order that is different than shown in process300.

FIG. 3B is a flowchart illustrating an example process 350 forcontrolling the operation of a stop plate of a charging system. The stopplate described in process 350 may include structural and/or operationalfeatures similar to stop plate 117 described with reference to FIG. 1A.Example process 350, or any portion thereof, may be implemented on, orexecuted, by a computing device, such as a processor and in someembodiments may be implemented on a processor of a controller of thecharging system described herein such as controller 111.

At block 352, the processor may detect the presence of a vehicle on thecharging system, for example a vehicle that has accessed the chargingsystem to be charged. The processor may detect the presence of a vehicleusing one or more sensors as described elsewhere herein and/or maydetect a vehicle based on user input, for example at the controller,that a vehicle is on the charging system, for example to be charged.

At block 354, the processor may cause a stop plate to be placed in anupward position, for example by sending instructions to an actuator ofthe stop plate. When in the upward position, the stop plate may preventthe vehicle from moving, for example rolling off a ramp of the chargingsystem and/or may maintain the vehicle in a substantially constantposition to facilitate a charging of the vehicle by facilitatingconsistent physical contact between the drive roller(s) and the wheel(s)of the vehicle.

At block 356 the processor may initiate a charging sequence. Thecharging sequence may include embodiments and implementation describedelsewhere herein such as an angular velocity at which to drive the driveroller(s), a time for which to drive the drive roller(s) and the like.

At block 358, the processor may maintain the stop plate in the upwardposition, for example while the vehicle is being charged during thecharge sequence. At block 360, the processor may determine whether thecharging sequence is complete. Block 360 may include similar embodimentsand implementations described with reference to block 268 of FIG. 2B.For example, the processor may determine whether a charge sequence iscomplete based on data received from the vehicle and/or user input, forexample at the controller.

If the charging sequence is not complete, the processor may return toblock 358 to keep the stop plate in the upward position. If the chargingsystem is complete, the processor may cause the stop plate to be placedin the downward position for example by sending instructions to anactuator of the stop plate. When in the downward position, the stopplate may allow the vehicle on the charging system to leave the chargingsystem, for example by allowing the vehicle to drive off of a ramp ofthe charging system.

Process 350 is provided as an example and is not intended to belimiting. In some embodiments, the processor may not implement all theblocks shown in process 350 or may implement additional blocks to thosethat are shown in process 350. In some embodiments, the processor mayexecute the blocks in an order that is different than shown in process350.

Additional Embodiments

As used herein, “system,” “instrument,” “apparatus,” and “device”generally encompass both the hardware (for example, mechanical andelectronic) and, in some implementations, associated software (forexample, specialized computer programs for graphics control) components.

It is to be understood that not necessarily all objects or advantagesmay be achieved in accordance with any particular embodiment describedherein. Thus, for example, those skilled in the art will recognize thatcertain embodiments may be configured to operate in a manner thatachieves or optimizes one advantage or group of advantages as taughtherein without necessarily achieving other objects or advantages as maybe taught or suggested herein.

Each of the processes, methods, and algorithms described in thepreceding sections may be embodied in, and fully or partially automatedby, code modules executed by one or more computer systems or computerprocessors including computer hardware. The code modules may be storedon any type of non-transitory computer-readable medium or computerstorage device, such as hard drives, solid state memory, optical disc,and/or the like. The systems and modules may also be transmitted asgenerated data signals (for example, as part of a carrier wave or otheranalog or digital propagated signal) on a variety of computer-readabletransmission mediums, including wireless-based and wired/cable-basedmediums, and may take a variety of forms (for example, as part of asingle or multiplexed analog signal, or as multiple discrete digitalpackets or frames). The processes and algorithms may be implementedpartially or wholly in application-specific circuitry. The results ofthe disclosed processes and process steps may be stored, persistently orotherwise, in any type of non-transitory computer storage such as, forexample, volatile or non-volatile storage.

Many other variations than those described herein will be apparent fromthis disclosure. For example, depending on the embodiment, certain acts,events, or functions of any of the algorithms described herein can beperformed in a different sequence, can be added, merged, or left outaltogether (for example, not all described acts or events are necessaryfor the practice of the algorithms). Moreover, in certain embodiments,acts or events can be performed concurrently, for example, throughmulti-threaded processing, interrupt processing, or multiple processorsor processor cores or on other parallel architectures, rather thansequentially. In addition, different tasks or processes can be performedby different machines and/or computing systems that can functiontogether.

The various illustrative logical blocks, modules, and algorithm elementsdescribed in connection with the embodiments disclosed herein can beimplemented as electronic hardware, computer software, or combinationsof both. To clearly illustrate this interchangeability of hardware andsoftware, various illustrative components, blocks, modules, and elementshave been described herein generally in terms of their functionality.Whether such functionality is implemented as hardware or softwaredepends upon the particular application and design constraints imposedon the overall system. The described functionality can be implemented invarying ways for each particular application, but such implementationdecisions should not be interpreted as causing a departure from thescope of the disclosure.

The various features and processes described herein may be usedindependently of one another or may be combined in various ways. Allpossible combinations and sub-combinations are intended to fall withinthe scope of this disclosure. In addition, certain method or processblocks may be omitted in some implementations. The methods and processesdescribed herein are also not limited to any particular sequence, andthe blocks or states relating thereto can be performed in othersequences that are appropriate. For example, described blocks or statesmay be performed in an order other than that specifically disclosed, ormultiple blocks or states may be combined in a single block or state.The example blocks or states may be performed in serial, in parallel, orin some other manner. Blocks or states may be added to or removed fromthe disclosed example embodiments. The example systems and componentsdescribed herein may be configured differently than described. Forexample, elements may be added to, removed from, or rearranged comparedto the disclosed example embodiments.

The various illustrative logical blocks and modules described inconnection with the embodiments disclosed herein can be implemented orperformed by a machine, such as a general purpose processor, a digitalsignal processor (“DSP”), an application specific integrated circuit(“ASIC”), a field programmable gate array (“FPGA”) or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general purpose processor can be a microprocessor,but in the alternative, the processor can be a controller,microcontroller, or state machine, combinations of the same, or thelike. A processor can include electrical circuitry configured to processcomputer-executable instructions. In another embodiment, a processorincludes an FPGA or other programmable devices that performs logicoperations without processing computer-executable instructions. Aprocessor can also be implemented as a combination of computing devices,for example, a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration. Although described hereinprimarily with respect to digital technology, a processor may alsoinclude primarily analog components. For example, some, or all, of thesignal processing algorithms described herein may be implemented inanalog circuitry or mixed analog and digital circuitry. A computingenvironment can include any type of computer system, including, but notlimited to, a computer system based on a microprocessor, a mainframecomputer, a digital signal processor, a portable computing device, adevice controller, or a computational engine within an appliance, toname a few.

The elements of a method, process, or algorithm described in connectionwith the embodiments disclosed herein can be embodied directly inhardware, in a software module stored in one or more memory devices andexecuted by one or more processors, or in a combination of the two. Asoftware module can reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of non-transitory computer-readable storagemedium, media, or physical computer storage known in the art. An examplestorage medium can be coupled to the processor such that the processorcan read information from, and write information to, the storage medium.In the alternative, the storage medium can be integral to the processor.The storage medium can be volatile or nonvolatile. The processor and thestorage medium can reside in an ASIC. The ASIC can reside in a userterminal. In the alternative, the processor and the storage medium canreside as discrete components in a user terminal.

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Disjunctive language such as the phrase “at least one of X, Y, or Z,”unless specifically stated otherwise, is otherwise understood with thecontext as used in general to present that an item, term, and so forth,may be either X, Y, or Z, or any combination thereof (for example, X, Y,and/or Z). Thus, such disjunctive language is not generally intended to,and should not, imply that certain embodiments require at least one ofX, at least one of Y, or at least one of Z to each be present.

Any process descriptions, elements, or blocks in the flow diagramsdescribed herein and/or depicted in the attached figures should beunderstood as potentially representing modules, segments, or portions ofcode which include one or more executable instructions for implementingspecific logical functions or steps in the process. Alternateimplementations are included within the scope of the embodimentsdescribed herein in which elements or functions may be deleted, executedout of order from that shown or discussed, including substantiallyconcurrently or in reverse order, depending on the functionalityinvolved, as would be understood by those skilled in the art.

Unless otherwise explicitly stated, articles such as “a” or “an” shouldgenerally be interpreted to include one or more described items.Accordingly, phrases such as “a device configured to” are intended toinclude one or more recited devices. Such one or more recited devicescan also be collectively configured to carry out the stated recitations.For example, “a processor configured to carry out recitations A, B andC” can include a first processor configured to carry out recitation Aworking in conjunction with a second processor configured to carry outrecitations B and C.

All of the methods and processes described herein may be embodied in,and partially or fully automated via, software code modules executed byone or more general purpose computers. For example, the methodsdescribed herein may be performed by the computing system and/or anyother suitable computing device. The methods may be executed on thecomputing devices in response to execution of software instructions orother executable code read from a tangible computer readable medium. Atangible computer readable medium is a data storage device that canstore data that is readable by a computer system. Examples of computerreadable mediums include read-only memory, random-access memory, othervolatile or non-volatile memory devices, CD-ROMs, magnetic tape, flashdrives, and optical data storage devices.

It should be emphasized that many variations and modifications may bemade to the herein-described embodiments, the elements of which are tobe understood as being among other acceptable examples. All suchmodifications and variations are intended to be included herein withinthe scope of this disclosure. The section headings used herein aremerely provided to enhance readability and are not intended to limit thescope of the embodiments disclosed in a particular section to thefeatures or elements disclosed in that section. The foregoingdescription details certain embodiments. It will be appreciated,however, that no matter how detailed the foregoing appears in text, thesystems and methods can be practiced in many ways. As is also statedherein, it should be noted that the use of particular terminology whendescribing certain features or aspects of the systems and methods shouldnot be taken to imply that the terminology is being re-defined herein tobe restricted to including any specific characteristics of the featuresor aspects of the systems and methods with which that terminology isassociated.

Those of skill in the art would understand that information, messages,and signals may be represented using any of a variety of differenttechnologies and techniques. For example, data, instructions, commands,information, signals, bits, symbols, and chips that may be referencedthroughout the above description may be represented by voltages,currents, electromagnetic waves, magnetic fields or particles, opticalfields or particles, or any combination thereof

What is claimed is:
 1. A system for charging a stationary electricvehicle using power generation or regeneration devices of the vehicle,the system comprising: a controller configured to: generate charginginstructions to charge the vehicle; and generate accessibilityinstructions to control access to the charging system; and a stop platein communication with the controller and configured to: transitionbetween an upward position and a downward position according to theaccessibility instructions received from the controller, wherein in theupward position, the stop plate is configured to prevent the vehiclefrom accessing the charging system to be charged, and wherein in thedownward position the stop plate is configured to allow the vehicle toaccess the charging system to be charged.
 2. The system of claim 1,further comprising one or more drive rollers rotatably coupled to one ormore wheels of the vehicle and configured to rotate, according to thecharging instructions, to cause the wheels of the vehicle to rotate tocause power generation or regeneration devices of the vehicle togenerate energy to store in an energy storage device of the vehicle. 3.The system of claim 1, wherein the controller is further configured to:receive a user input; and generate the charging instructions based, atleast in part, on the user input.
 4. The system of claim 1, wherein thecontroller is further configured to: receive operational settingsrelating to a charging sequence, wherein the operational settings arereceived from a memory of the controller, an external data store, or thevehicle; and generate the charging instructions based, at least in part,on the operational settings.
 5. The system of claim 1, wherein thecontroller is further configured to communicate with the vehicle totransmit data to the vehicle and receive data from the vehicle.
 6. Thesystem of claim 1, wherein the controller is further configured to:receive data from the vehicle relating to charging requirements of thevehicle; and generate the charging instructions based, at least in part,on the data received from the vehicle relating to the chargingrequirements.
 7. The system of claim 1, wherein the controller isfurther configured to receive data from the vehicle relating to anidentity of the vehicle or permissions of the vehicle to access thecharging system to be charged.
 8. The system of claim 7, wherein thecontroller is further configured to generate the accessibilityinstructions based at least in part on the identity of the vehicle orthe permissions of the vehicle.
 9. The system of claim 7, wherein thecontroller is further configured to: determine, based on the identity ofthe vehicle or the permissions of the vehicle, whether the vehicle haspermission to access the charging system to be charged; and in responseto determining that the vehicle has permission to access the chargingsystem, cause the stop plate to transition the downward position toallow the vehicle to access the charging system to be charged.
 10. Thesystem of claim 7, wherein the controller is further configured to:determine, based on the identity of the vehicle or the permissions ofthe vehicle, whether the vehicle has permission to access the chargingsystem to be charged; and in response to determining that the vehiclelacks permission to access the charging system, prevent the stop platefrom transitioning to the downward position to prevent the vehicle fromaccessing the charging system to be charged.
 11. A method for charging astationary electric vehicle using power generation or regenerationdevices of the vehicle, the method comprising: under control of aprocessor of a controller of a charging system: generating charginginstructions to charge the vehicle; and generating accessibilityinstructions to control access to the charging system; and transitioninga stop plate between an upward position and a downward positionaccording to the accessibility instructions received from thecontroller, wherein in the upward position, the stop plate is configuredto prevent the vehicle from accessing the charging system to be charged,and wherein in the downward position the stop plate is configured toallow the vehicle to access the charging system to be charged.
 12. Themethod of claim 11, further comprising causing one or more drive rollersto rotate according to the charging instructions to cause the wheels ofthe vehicle to rotate to cause power generation or regeneration devicesof the vehicle to generate energy to store in an energy storage deviceof the vehicle.
 13. The method of claim 11, further comprising:receiving, at the controller, user input; and generating theinstructions for the charging instructions based at least in part on theuser input.
 14. The method of claim 11, further comprising: receiving,at the controller, operational settings relating to a charging sequence,wherein the operational settings are received from a memory of thecontroller, an external data store, or the vehicle; and generating thecharging instructions based, at least in part, on the operationalsettings.
 15. The method of claim 11, further comprising: receiving, atthe controller, data from the vehicle relating to charging requirementsof the vehicle; and generating the charging instructions based, at leastin part, on the data received from the vehicle relating to the chargingrequirements.
 16. The method of claim 11, further comprising receiving,at the controller, data from the vehicle relating to an identity of thevehicle or permissions of the vehicle to access the charging system tobe charged.
 17. The method of claim 16, further comprising generatingthe accessibility instructions based at least in part on the identity ofthe vehicle or the permissions of the vehicle.
 18. The method of claim16, further comprising: determining, based on the identity of thevehicle or the permissions of the vehicle, whether the vehicle haspermission to access the charging system to be charged; and in responseto determining that the vehicle has permission to access the chargingsystem, causing the stop plate to transition the downward position toallow the vehicle to access the charging system to be charged.
 19. Themethod of claim 16, further comprising: determining, based on theidentity of the vehicle or the permissions of the vehicle, whether thevehicle has permission to access the charging system to be charged; andin response to determining that the vehicle lacks permission to accessthe charging system, preventing the stop plate from transitioning to thedownward position to prevent the vehicle from accessing the chargingsystem to be charged.
 20. The method of claim 16, further comprising:determining, based on the identity of the vehicle or the permissions ofthe vehicle, whether the vehicle has permission to access the chargingsystem to be charged; and in response to determining that the vehiclelacks permission to access the charging system, causing the stop plateto transition to the upward position to prevent the vehicle fromaccessing the charging system to be charged.